Re-deploy 2026.03.000 After Workflow Error#35
Merged
Conversation
…est so release workflow runs on merge
bschroeter
approved these changes
Apr 20, 2026
Collaborator
bschroeter
left a comment
bschroeter
left a comment
There was a problem hiding this comment.
LGTM, keen to see the infra response to this.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Redeploy of #34
Background
On the infrastructure side of things, we're currently updating our spack instances to use a new version of
spack-config. The workflow can handle it for prerelease, but we haven't yet got around to it working for release instances. This temporary tag forbuild-cdwill be used to deploy the above2026.03.000release while we migrate the release instances.The PR